Data Services Developer's Guide : How To Create Physical Data Services Based on Database Functions
This page last changed on Jan 09, 2008 by tkatz.
eDocs Home > BEA AquaLogic Data Services Platform 3.0 Documentation > Data Services Developer's Guide
|
![]() | A library data service created based on database functions is restricted to that type of function. For example, a library function based on a stored procedure cannot be added to a library data service that contains database functions. |
You can use the the physical data service creation wizard to:
Physical data services are created using a wizard.
To start the physical data service creation wizard:
When importing a relational object available options include the ability to:
Relational Type | Description |
---|---|
Tables and Views |
Displays all public tables and views in the selected data source. |
Stored Procedures |
Displays all public stored procedures in the selected data source. |
SQL Statement |
Allows creation of a SQL statement for extracting relational data from the data source. |
Database Function |
Allows creation of an XQuery function in a library data service based on build-in or custom database functions. |
Option | Action |
Comment/Reference |
---|---|---|
Catalog: |
Enter catalog name, if needed by your RDBMS |
|
Schema: |
Enter schema name, if needed by your RDBMS | |
Package: | Enter package name, if needed by your RDBMS | |
Function name: |
Database function name |
Required. |
XQuery function |
XQuery function name |
Required; will invoke the database function. |
Public | Select, if you want to make your operation public |
Default for created XQuery functions is protected. |
|
Click Next |
|
Review |
Enter library data service name |
If the name of an existing library data service is provided. |
![]() | There is no type checking or other type of verification regarding external function parameters. |
On the Review New Data Service(s) page you can set, confirm or, optionally, change suggested data service names depending on the type of physical data service you are creating.
The nominated name for a new data service is, wherever possible, the same as the source object name. In some cases, however, names are adjusted to conform with XML naming conventions.
![]() | XML Name Conversion Considerations |
Name conflicts occur when there is a data service of the same name present in the target directory. Name conflicts are highlighted in red.
There are several situations where you will need to change the name of your data service:
Data services always have the file extension:
.ds
![]() |
Document generated by Confluence on Jan 15, 2008 11:02 |